chore: manage admin repo with safe-settings#14
Merged
nbrieussel merged 3 commits intomainfrom Apr 14, 2026
Merged
Conversation
Closes #9 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
No technical reason to exclude it in GitHub Actions mode. Safe-settings reads config from this repo and can apply settings to it at the same time. org-wide settings.yml will now govern the admin repo like any other repo. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Remove
adminfromrestrictedRepos.excludeindeployment-settings.yml.Why
No technical reason to exclude it in GitHub Actions mode — safe-settings reads config from this repo and can apply settings to it simultaneously. The org-wide
settings.ymlwill now governadminlike any other repo (labels, branch protection withnbrieusselbypass, merge strategy, etc.).The
delete_branch_on_merge: truewe just set manually via the API will be maintained by safe-settings going forward.Dry-run checklist
gh workflow run safe-settings-sync.yml --repo IntegratedDynamic/admin --ref chore/manage-admin-with-safe-settings -f nop=trueadminrepo (first time it gets managed)